feat: add developer-gated Prompt Shortcuts [risk:high] - #575

…sk:high]

Settings now reads as the same surface as Agent Roles and MCP: one dialog
header/scroll/footer editor built from the shared `form-primitives` grammar,
Radix selects for the three scope axes, a Switch for sharing with its
visibility warning, and the shared catalog row. Adds scope pills, per-row
publication state, a read-only view for another member's shared Shortcut, and
disabled mention kinds that name the scope axes they still need.

Also carries this branch's local-first storage work: a separate local ledger,
write intents and immutable publication jobs, so a pending publication stays
durable without ever blocking Save or Delete.

Slash invocation, the variable argument tray and composer send integration
remain follow-up work.

Model: claude-opus-5

Scope moves out of its own section and sits inline above the prompt input,
each axis naming itself in its trigger, with the explanation folded into the
prompt hint. The description field says what it is and where it shows, a
variable's default sits beside its name instead of under it, and the prompt
box starts shorter.

Model: claude-opus-5

A default value is usually a few words, so the field starts at a single row
and tracks its content instead of reserving two. `AutoGrowTextarea` joins the
shared settings primitives, and re-measures on width changes because wrapping
is what decides the row count.

Model: claude-opus-5

Add independent Slash discovery, cancellable snapshot selection, inline invocation parameters, isolated draft recovery, and ordered prompt compilation with expand-and-edit support.

Model: gpt-6

Reuse the shared composer mention portal within the nearest modal and constrain desktop and mobile positioning to its bounds. Cover real Shortcut creation dialogs in Storybook and modal selection in regression tests.

Model: gpt-6

…sk:medium]

The tray now reads as the settings variable editor it mirrors: the `!{name}`
token beside its value, growing from one row, a missing value tinting its own
token instead of adding an asterisk. Desktop keeps a section header with the
dismiss action; mobile keeps the sheet with a full-width Done.

"Expand and edit" is removed. It existed to change a template's body, which
Settings already does — durably, for every invocation — and it paid for that
with a whole draft vocabulary of its own: generated unresolved markers, literal
ranges that stop substituted text being rescanned, their persistence and undo
rules, and an extra send-time check for leftover markers. A chip is atomic
again, so all of that goes with it.

Model: claude-opus-5

The catalog row was four left-aligned lines against an empty right half. It is
now two: identity reads down the left, and what the author set — scope, variable
count — plus what is happening to it sit against the right edge. Both halves
wrap rather than switching on a viewport breakpoint, because settings render in
a panel far narrower than the window. Status copy shortens to phrases that fit
that column.

The tray drops the "fill these variables" line between the prompt and the
fields and sits against the invocation instead. The chip's own badge and the
tinted token already name what is missing; a third sentence only pushed the
fields away from the thing they belong to.

Model: claude-opus-5

A Shortcut carries an optional `emoji`, normalized on the way in and projected
into the index so the list can show it without loading a body. It replaces the
`/` glyph in the catalog tile; unset renders the default rather than an empty
slot. The emoji control itself moves out of the Agent Role editor into
`settings/emoji-field.tsx`, so the two editors cannot grow two of them.

Also drops the `!N` badge painted over an invocation chip — the chip already
turns red and the tray names the values — and with it the mention primitive's
`badge` slot, which had no other caller.

While a parameter tray is open the composer stops reserving its blank writing
rows: those rows are room for writing, and reserving them above the tray left a
band of empty box between the `/command` and the fields it belongs to.

Model: claude-opus-5

…k:medium]

Four things the composer and the catalog were getting wrong:

Clearing the prompt to empty dropped focus. The reset remounts the mention tree
to re-arm the hydrators, which replaces the textarea node; restoring focus was
conditional on the caller having passed a ref, and the settings template editor
passes none. The component keeps its own ref now and hands the node to the
forwarded one as well.

The catalog reported background publication. A local save is already durable and
the runtime retries on its own, so neither state is something a reader can act on
from a row. The only status left is the one its author must repair: a reference
that no longer fits the saved scope.

The `/` menu shows each Shortcut's own emoji, the way an Agent Role's row does.

A chip now carries the values that were filled into it (`shortcutChipText`,
applied on tray close), capped by code points so a truncation cannot split a
surrogate pair. A draft of three identical `/review` chips was not something
anyone could check before sending. Both forms of the text stay valid, so a draft
stored before its values still restores.

Model: claude-opus-5

A Shortcut is a Prompt and a scope now, nothing else. `!{name}` is ordinary
text: stored, expanded and sent exactly as written.

Gone from the model: the `variables` field, its schema and byte limits, the
index's `variableCount`, placeholder parsing and escaping, value injection, the
`missing_variables` error code, and `updateShortcutInvocation` (which existed
only to migrate values across a reload). `ShortcutInvocation` is `{ id,
snapshot }`, so `expandShortcut` is a straight lowering of the snapshot's text
and mentions.

Gone from the UI: the Settings variables section, the composer's parameter tray
and bottom sheet, their send gate, the chip's missing-count colouring, and the
value label a chip carried. What remains of the composer bridge is
`shortcut-invocation-status.tsx` — why an inserted chip cannot be sent, which is
about live context rather than anything the caller types.

The invocation schema is deliberately not strict: a draft stored while values
existed still restores, minus the ignored key.

Model: claude-opus-5

Default the opt-in off and share the developer-mode gate across settings navigation, direct panel access, mention selection and the workspace runtime. Preserve saved data and cover toggle transitions and late selection results.

Model: gpt-6

Clear the Shortcut checkpoint before successful landing navigation, fenced by composer mount and draft identity so late session acceptance cannot delete or navigate a replacement draft. Add deterministic recovery regressions and satisfy the branch formatting gate.

Model: gpt-6

Model: gpt-6

Model: gpt-6

Model: gpt-6

Model: gpt-6

Preserve Agent Role schema reconciliation inside the Shortcut provider.

Model: gpt-6

Model: gpt-6